-
Notifications
You must be signed in to change notification settings - Fork 75
New: Python - Switch Environments / Update: Python - Create Virtual Environments / Update: Python Virtual environment #219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: SundareshSankaran <[email protected]>
Continuing my new practice of starting a Draft PR (to signal my plans in advance).
|
Signed-off-by: SundareshSankaran <[email protected]>
Signed-off-by: SundareshSankaran <[email protected]>
Signed-off-by: SundareshSankaran <[email protected]>
… venv Signed-off-by: SundareshSankaran <[email protected]>
Signed-off-by: SundareshSankaran <[email protected]>
Signed-off-by: SundareshSankaran <[email protected]>
…ginal-environment
Signed-off-by: SundareshSankaran <[email protected]>
…ttps://github.com/SundareshSankaran/sas-studio-custom-steps into 49-update-python---revert-to-original-environment
PR for review. As part of exercise to revamp existing Python Virtual Environments, this is the second on the list. I expect a final contribution (combining Obtain requirements and Freeze requirements) to round off the list. Note that over the course of testing this, I found a condition in Create a Virtual Environment that breaks this step. Therefore, this PR also contains an update to the Create a Virtual Environment step. Please let me know in case of any questions. |
Signed-off-by: SundareshSankaran <[email protected]>
@SundareshSankaran , as you also included an update to the Python - Create Virtual Environments step in this same PR, you should also include an updated README.md for that step with a change log that also lists the new x.x.1 version and an explanation. The About tab of that step should reference that new updated version number if it didn't do so already. |
…cro handling Signed-off-by: SundareshSankaran <[email protected]>
Thanks, @snlwih , I pushed the same just now. ![]() |
…ginal-environment
Updated notes to use GitHub Alert notation, so it shows a colorfoul icon. Signed-off-by: snlwih <[email protected]>
Repeated note that points to replacement steps in sections for each individual step that is impacted. Signed-off-by: snlwih <[email protected]>
SAS Internal Due Diligence Review - COMPLETED on 02SEP2025 |
Please include answers to these questions as part of your pull request
In the GitHub webUI, use the Write tab to modify the Markdown text that is part of the pull request. For each question simply place an X inside the square brackets, [X], that represents your answer. Make sure there are no blanks inside the brackets, otherwise MarkDown doesn't render properly. Using the Preview tab while editing this form, you can see the formatted/rendered version of the message.